The purpose of the Role/System matrix is to depict the relationship between systems (i.e., application components) and the business roles that use them within the enterprise.

People in an organization interact with systems. During this interaction, these people assume a specific role to perform a task; for example, product buyer.

The mapping of the Application Component-Role relationship is an important step as it enables the following to take place:

• Assign usage of applications to the specific roles in the organization
• Understand the application security requirements of the business services and processes supporting the function, and check these are in line with current policy
• Support the gap analysis and determine whether any of the applications are missing and as a result need to be created
• Define the application set used by a particular business role; essential in any move to role-based computing

The Role/System matrix is a two-dimensional table with Logical Application Component on one axis and Role on the other axis.

The relationship between these two entities is a composite of a number of metamodel relationships that need validating:

• Role accesses Function
• Function is bounded by Service
• Services are realized by Logical/Physical Application Components